Searched: \.*
Results from Gpce web
The International Conference on Generative Programming and Component Engineering (GPCE) Bylaws
Organizational Goals
Program generation techniques have the potential to revolutionize software development as automation and components revolutionized manufacturing. The abundance of current research in this area indicates that there are many technical problems both at the foundational and engineering levels. There is wealth of methods in approaching problems from different backgrounds, and a wide spectrum of application domains were program generation techniques appear valuable. This diversity may lead to unnecessary fragmentation in the research community. The major aim of GPCE is to foster the creation of a bridge community, in addition to communities with more specific interests and goals.
Affiliation with ACM and IFIP
GPCE will seek the sponsorship of the ACM whenever possible. In additional to its independent standing as a conference, GPCE also serves as the working conference for the IFIP Working Group on Program Generation, WG 2.11.
Organizational Structure
The organizational structure of GPCE consists of a single Steering Committee whose aim is to promote the coherent aggregation of related events. The GPCE conference takes place yearly, in the August to October period (typically Sepptember to October). For the purposes of the following, a year ends on the date of conclusion of the calendar year's GPCE conference. For example, if the GPCE conference runs September 28 - October 2, October 31 concludes the calendar year.
Steering Committee
MEMBERSHIP. The Steering Committe (SC) is limited to six (6) members. Each member can serve for at most five (5) years. In normal circumstances, each year the oldest member leaves the SC, and is replaced by a new member as indicated below. Incoming SC members are chosen by SC decision among:
- the General Chairs (GCs) of the last 3 GPCE conferences
- the Program Chairs (PCs) of the last 3 GPCE conferences
- suggesting changes to the bylaws
- appointing the GPCE GC and PC (and other persons involved in the organization of one edition of GPCE), and specifying their duties
- making decisions on matters that have a lasting consequences on GPCE conference, such as: the scope, topics of interests, publication venues
- making decisions on information sharing infrastructures to promote interaction and dissemination of ideas in the GPCE community, such as mailing lists, repositories, web sites.
- appointing the GPCE Publicity Chair or other persons involved in the organization of several editions of GPCE (or in managing the information sharing infrastructures), and specifying their duties
Business Meetings
Each GPCE conference should schedule a Business Meeting (BM), which is public and conducted by the SC chair (or a deputy from the SC). The BM is a way to provide information to and get feedback from the GPCE community. The BM typically includes the following items:
- a report on the current GPCE conference
- an announcement of next year's GPCE conference
- offers from potential host for the GPCE in two years
The International Conference on Generative Programming and Component Engineering (GPCE)
Bylaws
Aim
Program generation techniques have the potential to revolutionize software development as automation and components revolutionized manufacturing. The abundance of current research in this area indicates that there are many technical problems both at the foundational and engineering levels. There is wealth of methods in approaching problems from different backgrounds, and a wide spectrum of application domains were program generation techniques appear valuable. This diversity may lead to unnecessary fragmentation in the research community. The major aim of GPCE is to foster the creation of a bridge community, in addition to communities with more specific interests. The organizational structure of GPCE consists of a single Steering Committee whose aim is to promote the coherent aggregation of related events. Affiliation with ACM and IFIP
GPCE will seek the sponsorship of the ACM whenever possible. In additional to its independent standing as a conference, GPCE also serves as the working conference for the IFIP Working Group on Program Generation, WG 2.11. Steering Committee
GPCE takes place yearly, in the August to October period (typically Sep-Oct). For the purposes of the following, a year ends on the date of conclusion of the calendar year's GPCE conference. The Steering Committe (SC) is limited to SIX members. {ADD - Each member can serve for at most 5 years.} In normal circumstances, each year the oldest member leaves the SC, and is replaced by a new person. A decision is deemed approved by the SC by majority rule; votes that end in ties are not approved. {A.1 CURRENT - The person serving the 5th year of membership is committee chair for that year}{A.2 NEW - The SC votes one of its members SC chair, with a 2 year mandate.}. The SC chair is the official representative of the SC within GPCE and the official interface between the SC and the outside world. The chair is expected to lead the discussion within the SC and coordinate the activities of the SC. Incoming SC members are chosen by SC decision among: * the General Chairs (GCs) of the last 3 GPCE conferences * the Program Chairs (PCs) of the last 3 GPCE conferences In special circumstances (namely bootstrapping: not enough eligible persons per above rules) the current SC is allowed to select members outside the above categories. {B.1 CURRENT - When a person leaves the SC, by default all people in the SC with earlier rank are promoted, so that the newest person will have least seniority. The default may be altered by an SC decision. But under no circumstances will a SC member serve more than 5 years in a single appointment.}{B.2 NEW - drop this part} The SC (based on the ACM guidelines) is responsible for * specifying the duties of the SC including changes to the bylaws * setup rules for appointing the GPCE GC and PC (and other persons involved in the organization of one edition of GPCE), and specifying their duties * making decisions on matters that have a lasting consequences on GPCE conference, such as: the scope, topics of interests, publication venues * making decisions on information sharing infrastructures to promote interaction and dissemination of ideas in the GPCE community, such as mailing lists, repositories, web sites. * appointing the GPCE Publicity Chair or other persons involved in the organization of several editions of GPCE (or in managing the information sharing infrastructures), and specifying their duties Business Meetings
Each GPCE conference should schedule a Business Meeting (BM), which is public and conducted by the SC chair (or a deputy from the SC). The BM is a way to provide information to and get feedback from the GPCE community. The BM typically includes the following items: * a report on the current GPCE conference * an announcement of next year's GPCE conference * offers from potential host for the GPCE in two years Proposals for additional items should be brought to the attention of SC members at least two months in advance of the BM, but a limited time for raising unanticipated issues is always granted. The agenda of the BM will be finalized at least one month in advance. During the BM a show of hands could be taken on specific issues, but the result is not binding for the SC.
Program generation techniques have the potential to revolutionize software development as automation and components revolutionized manufacturing. The abundance of current research in this area indicates that there are many technical problems both at the foundational and engineering levels. There is wealth of methods in approaching problems from different backgrounds, and a wide spectrum of application domains were program generation techniques appear valuable. This diversity may lead to unnecessary fragmentation in the research community. The major aim of GPCE is to foster the creation of a bridge community, in addition to communities with more specific interests. The organizational structure of GPCE consists of a single Steering Committee whose aim is to promote the coherent aggregation of related events. Affiliation with ACM and IFIP
GPCE will seek the sponsorship of the ACM whenever possible. In additional to its independent standing as a conference, GPCE also serves as the working conference for the IFIP Working Group on Program Generation, WG 2.11. Steering Committee
GPCE takes place yearly, in the August to October period (typically Sep-Oct). For the purposes of the following, a year ends on the date of conclusion of the calendar year's GPCE conference. The Steering Committe (SC) is limited to SIX members. {ADD - Each member can serve for at most 5 years.} In normal circumstances, each year the oldest member leaves the SC, and is replaced by a new person. A decision is deemed approved by the SC by majority rule; votes that end in ties are not approved. {A.1 CURRENT - The person serving the 5th year of membership is committee chair for that year}{A.2 NEW - The SC votes one of its members SC chair, with a 2 year mandate.}. The SC chair is the official representative of the SC within GPCE and the official interface between the SC and the outside world. The chair is expected to lead the discussion within the SC and coordinate the activities of the SC. Incoming SC members are chosen by SC decision among: * the General Chairs (GCs) of the last 3 GPCE conferences * the Program Chairs (PCs) of the last 3 GPCE conferences In special circumstances (namely bootstrapping: not enough eligible persons per above rules) the current SC is allowed to select members outside the above categories. {B.1 CURRENT - When a person leaves the SC, by default all people in the SC with earlier rank are promoted, so that the newest person will have least seniority. The default may be altered by an SC decision. But under no circumstances will a SC member serve more than 5 years in a single appointment.}{B.2 NEW - drop this part} The SC (based on the ACM guidelines) is responsible for * specifying the duties of the SC including changes to the bylaws * setup rules for appointing the GPCE GC and PC (and other persons involved in the organization of one edition of GPCE), and specifying their duties * making decisions on matters that have a lasting consequences on GPCE conference, such as: the scope, topics of interests, publication venues * making decisions on information sharing infrastructures to promote interaction and dissemination of ideas in the GPCE community, such as mailing lists, repositories, web sites. * appointing the GPCE Publicity Chair or other persons involved in the organization of several editions of GPCE (or in managing the information sharing infrastructures), and specifying their duties Business Meetings
Each GPCE conference should schedule a Business Meeting (BM), which is public and conducted by the SC chair (or a deputy from the SC). The BM is a way to provide information to and get feedback from the GPCE community. The BM typically includes the following items: * a report on the current GPCE conference * an announcement of next year's GPCE conference * offers from potential host for the GPCE in two years Proposals for additional items should be brought to the attention of SC members at least two months in advance of the BM, but a limited time for raising unanticipated issues is always granted. The agenda of the BM will be finalized at least one month in advance. During the BM a show of hands could be taken on specific issues, but the result is not binding for the SC.
| Web | TWiki Site Map | Use to... |
|---|---|---|
Main     |
The Main web is dedicated to the maintenance of this website. This is the place to discuss meta-issues such as what style to use, how best to organize a survey, what the ideal topic size is, how to refer to papers, what the preferred layout of the site should be, etc. | ... |
| TWiki |
Welcome, Registration, and other StartingPoints; TWiki history & Wiki style; All the docs... | ...discover TWiki details, and how to start your own site. |
| Gmt |
Generative Model Transformer | |
| Gpce |
||
| Octave |
The Stratego web is the home of Stratego, a language for program transformation based on the paradigm of rewriting strategies. The aim of this language is to provide an expressive and declarative language for expressing all kinds of program transformations. The web includes publications on Stratego, download of the StrategoCompiler, documentation, and descriptions of applications. | ... |
| Sandbox |
Sandbox test area with all features enabled. | ...experiment in an unrestricted hands-on web. |
| Sdf |
The Sdf web is dedicated to the modular syntax definition formalism SDF. Here you can find implementations, pointers to download pages, syntax definitions for common languages, discussions about new features and implementatios of SDF, and tips and tricks for using the formalism. | ... |
| SdfBackup |
The Sdf web is dedicated to the modular syntax definition formalism SDF. Here you can find implementations, pointers to download pages, syntax definitions for common languages, discussions about new features and implementatios of SDF, and tips and tricks for using the formalism. | ... |
| Stratego |
The Stratego web is the home of Stratego, a language for program transformation based on the paradigm of rewriting strategies. The aim of this language is to provide an expressive and declarative language for expressing all kinds of program transformations. The web includes publications on Stratego, download of the StrategoCompiler, documentation, and descriptions of applications. | ... |
| Sts |
The Sofware Transformation Systems wiki | |
| Tiger |
Home of the Tiger in Stratego project, which is concerned with the exploration of transformation techniques in compilation using an implementation of a Tiger compiler. | ... |
| Tools |
The Tools web is the home of the XT? bundle of program transformation tools. XT is an open framework for program transformation based on the ATerm format for exchange of programs between tools. The bundle includes packages for parsing, pretty-printing, term rewriting, and grammar recovery. It also contains a distribution of the SDF2? GrammarBase?. The OnlinePackageBase is an open collection of packages for program transformation supporting package bundling on demand. | ... |
| Transform |
The Transform web is an attempt to get an overview of program transformation research and application. In the first place the web is a collection of resources such as pointers to researchers, conferences, journals, summaries and reviews of papers, and tools for implementing transformation systems. In the second place the Transform web attempts to bring structure in the world of program transformation by means of categories, taxonomies such as the TransformationTaxonomy, and entry points such as the ReengineeringWiki and the DeCompilation page. | ... |
| You can use color coding by web for identification and reference. This table is updated automatically based on WebPreferences settings of the individual webs. Contact webmaster@strategoxt.org if you need a separate collaboration web for your team. See also AdminTools. | ||
| Legend of icons: |
= Go to the home of the web = Search the web
|
= See recent changes in the web = Subscribe to get notified of changes by e-mail
|
The GPCE Steering Committee
Members
| Bernd Fischer (SA) (2011-) |
| Ewen Denney (USA) (2012-) |
| Matthew Flatt (USA) (2014-) |
| Jaakko Jarvi (USA) (2010-) |
| Christian Kästner (USA) (2013-) |
| Ulrik Pagh Schultz (DK) (2012-) |
| Eelco Visser (NL), Chair (2008-2012, ex-officio member 2012-) |
Past Members
| Jeremy Siek (US) (2008-2013) |
| Julia Lawall (FR) (2008-2013) |
| Charles Consel Chair (FR), (2007-2012) |
| Stanislaw Jarzabek (SG), (2005-2010) |
| Yannis Smaragdakis (US) (2003-2008) |
| Eugenio Moggi (IT), (2000-2008) |
| Krzysztof Czarnecki (CA), (2000-2008) |
| Ulrich Eisenecker (DE), (2000-2008) |
| Tim Sheard (US), (2000-2008) |
| Janos Sztipanovits (US), (2003-2005) |
| Greg Morrisett (US), (2000-2005) |
| Walid Taha (US), Founder, (2000-2007) |
| Frank Pfenning (US) (2003-2007) |
| Don Batory (US) (2000-2007) |
| Topic | Changed | By |
|---|---|---|
| WebLeftBar | 24 Sep 2018 - 19:13 | EelcoVisser |
| WebHome | 24 Sep 2018 - 19:13 | EelcoVisser |
| WebPreferences | 19 Mar 2015 - 12:36 | ChristianKaestner |
| SteeringCommittee? | 08 Nov 2013 - 06:54 | EelcoVisser |
| GpceBylaws? | 31 Aug 2013 - 11:39 | EelcoVisser |
| WebStatistics | 23 Feb 2010 - 07:58 | TWikiAdminGroup |
| ProposedBylawsBatory? | 03 Jun 2008 - 07:40 | EugenioMoggi |
| WebNotify | 02 Jul 2006 - 03:11 | EmirPasalic |
| WebNews | 28 Jun 2006 - 05:48 | EmirPasalic |
| CustomSiteMenus? | 19 Jun 2006 - 16:28 | EmirPasalic |
| WebView? | 14 Nov 2005 - 20:03 | WalidTaha |
| WebRss | 16 Aug 2004 - 03:27 | PeterThoeny |
| WebSearchAdvanced | 18 Jan 2004 - 10:52 | PeterThoeny |
| UpdateWebPages | 20 Sep 2002 - 08:37 | EelcoVisser |
| SiteMap | 27 Aug 2002 - 08:00 | EelcoVisser |
| WebChanges500 | 23 Apr 2002 - 20:09 | EelcoVisser |
| WebChanges200 | 23 Apr 2002 - 20:05 | EelcoVisser |
| WebChanges100 | 23 Apr 2002 - 19:53 | EelcoVisser |
| WebChanges | 23 Apr 2002 - 19:46 | EelcoVisser |
| WebIndex | 23 Jan 2002 - 14:20 | EelcoVisser |
| WebTopicList | 24 Nov 2001 - 11:40 | PeterThoeny |
| WebTools | 08 Nov 2001 - 09:49 | TWikiGuest |
| WebSearch | 08 Aug 2001 - 05:26 | PeterThoeny |
| Topic | Changed | By |
|---|---|---|
| WebLeftBar | 24 Sep 2018 - 19:13 | EelcoVisser |
| WebHome | 24 Sep 2018 - 19:13 | EelcoVisser |
| WebPreferences | 19 Mar 2015 - 12:36 | ChristianKaestner |
| SteeringCommittee? | 08 Nov 2013 - 06:54 | EelcoVisser |
| GpceBylaws? | 31 Aug 2013 - 11:39 | EelcoVisser |
| WebStatistics | 23 Feb 2010 - 07:58 | TWikiAdminGroup |
| ProposedBylawsBatory? | 03 Jun 2008 - 07:40 | EugenioMoggi |
| WebNotify | 02 Jul 2006 - 03:11 | EmirPasalic |
| WebNews | 28 Jun 2006 - 05:48 | EmirPasalic |
| CustomSiteMenus? | 19 Jun 2006 - 16:28 | EmirPasalic |
| WebView? | 14 Nov 2005 - 20:03 | WalidTaha |
| WebRss | 16 Aug 2004 - 03:27 | PeterThoeny |
| WebSearchAdvanced | 18 Jan 2004 - 10:52 | PeterThoeny |
| UpdateWebPages | 20 Sep 2002 - 08:37 | EelcoVisser |
| SiteMap | 27 Aug 2002 - 08:00 | EelcoVisser |
| WebChanges500 | 23 Apr 2002 - 20:09 | EelcoVisser |
| WebChanges200 | 23 Apr 2002 - 20:05 | EelcoVisser |
| WebChanges100 | 23 Apr 2002 - 19:53 | EelcoVisser |
| WebChanges | 23 Apr 2002 - 19:46 | EelcoVisser |
| WebIndex | 23 Jan 2002 - 14:20 | EelcoVisser |
| WebTopicList | 24 Nov 2001 - 11:40 | PeterThoeny |
| WebTools | 08 Nov 2001 - 09:49 | TWikiGuest |
| WebSearch | 08 Aug 2001 - 05:26 | PeterThoeny |
| Topic | Changed | By |
|---|---|---|
| WebLeftBar | 24 Sep 2018 - 19:13 | EelcoVisser |
| WebHome | 24 Sep 2018 - 19:13 | EelcoVisser |
| WebPreferences | 19 Mar 2015 - 12:36 | ChristianKaestner |
| SteeringCommittee? | 08 Nov 2013 - 06:54 | EelcoVisser |
| GpceBylaws? | 31 Aug 2013 - 11:39 | EelcoVisser |
| WebStatistics | 23 Feb 2010 - 07:58 | TWikiAdminGroup |
| ProposedBylawsBatory? | 03 Jun 2008 - 07:40 | EugenioMoggi |
| WebNotify | 02 Jul 2006 - 03:11 | EmirPasalic |
| WebNews | 28 Jun 2006 - 05:48 | EmirPasalic |
| CustomSiteMenus? | 19 Jun 2006 - 16:28 | EmirPasalic |
| WebView? | 14 Nov 2005 - 20:03 | WalidTaha |
| WebRss | 16 Aug 2004 - 03:27 | PeterThoeny |
| WebSearchAdvanced | 18 Jan 2004 - 10:52 | PeterThoeny |
| UpdateWebPages | 20 Sep 2002 - 08:37 | EelcoVisser |
| SiteMap | 27 Aug 2002 - 08:00 | EelcoVisser |
| WebChanges500 | 23 Apr 2002 - 20:09 | EelcoVisser |
| WebChanges200 | 23 Apr 2002 - 20:05 | EelcoVisser |
| WebChanges100 | 23 Apr 2002 - 19:53 | EelcoVisser |
| WebChanges | 23 Apr 2002 - 19:46 | EelcoVisser |
| WebIndex | 23 Jan 2002 - 14:20 | EelcoVisser |
| WebTopicList | 24 Nov 2001 - 11:40 | PeterThoeny |
| WebTools | 08 Nov 2001 - 09:49 | TWikiGuest |
| WebSearch | 08 Aug 2001 - 05:26 | PeterThoeny |
| Topic | Changed | By |
|---|---|---|
| WebLeftBar | 24 Sep 2018 - 19:13 | EelcoVisser |
| WebHome | 24 Sep 2018 - 19:13 | EelcoVisser |
| WebPreferences | 19 Mar 2015 - 12:36 | ChristianKaestner |
| SteeringCommittee? | 08 Nov 2013 - 06:54 | EelcoVisser |
| GpceBylaws? | 31 Aug 2013 - 11:39 | EelcoVisser |
| WebStatistics | 23 Feb 2010 - 07:58 | TWikiAdminGroup |
| ProposedBylawsBatory? | 03 Jun 2008 - 07:40 | EugenioMoggi |
| WebNotify | 02 Jul 2006 - 03:11 | EmirPasalic |
| WebNews | 28 Jun 2006 - 05:48 | EmirPasalic |
| CustomSiteMenus? | 19 Jun 2006 - 16:28 | EmirPasalic |
| WebView? | 14 Nov 2005 - 20:03 | WalidTaha |
| WebRss | 16 Aug 2004 - 03:27 | PeterThoeny |
| WebSearchAdvanced | 18 Jan 2004 - 10:52 | PeterThoeny |
| UpdateWebPages | 20 Sep 2002 - 08:37 | EelcoVisser |
| SiteMap | 27 Aug 2002 - 08:00 | EelcoVisser |
| WebChanges500 | 23 Apr 2002 - 20:09 | EelcoVisser |
| WebChanges200 | 23 Apr 2002 - 20:05 | EelcoVisser |
| WebChanges100 | 23 Apr 2002 - 19:53 | EelcoVisser |
| WebChanges | 23 Apr 2002 - 19:46 | EelcoVisser |
| WebIndex | 23 Jan 2002 - 14:20 | EelcoVisser |
| WebTopicList | 24 Nov 2001 - 11:40 | PeterThoeny |
| WebTools | 08 Nov 2001 - 09:49 | TWikiGuest |
| WebSearch | 08 Aug 2001 - 05:26 | PeterThoeny |
Introduction
As the commercial production of software systems moves towards being a traditional industry, automation will necessarily play a more substantial role in this industry, just as it plays a key role in the production of traditional commodities such as garments, automobiles, chemicals, and electronics. GPCE is a conference promoting the application and innovation of foundational techniques for supporting automatic program generation.- GPCE-news mailing list (Low-bandwidth: 2-10 msgs/yr).
Earlier events
- GPCE'18: GPCE'18
- GPCE'17: GPCE'17
- GPCE'16: GPCE'16
- GPCE'15: GPCE'15
- GPCE'14: GPCE'14
- GPCE'13: GPCE'13
- GPCE'12: GPCE'12
- GPCE'11: GPCE'11
- GPCE'10: GPCE'10
- GPCE'09: GPCE'09
- GPCE'08: GPCE'08
- GPCE'07: GPCE'07
- GPCE'06: GPCE'06
- GPCE'05: homepage.
- GPCE'04: homepage.
- GPCE'03
- GPCE'02: Pittsburgh
- SAIG'01
- SAIG'00
Background
Preferences:- Set WEBICON=http://www.hope.cs.rice.edu/twiki/pub/GPCE06/WebHome/gpce-logo.jpg
- Web specific background color: (Pick a lighter one of the StandardColors)
- Set WEBBGCOLOR = #D0D0D0
- Exclude web from a
web="all"search: (Set toonfor hidden webs)- Set NOSEARCHALL =
- Set SITEMAPLIST = on
- Default template for new topics and form(s) for this web:
- WebTopicEditTemplate?: Default template for new topics in this web. (Site-level is used if topic does not exist)
- TWiki.WebTopicEditTemplate: Site-level default template
- TWikiForms: How to enable form(s)
- Set WEBFORMS =
- Users or groups who are not / are allowed to view / change / rename topics in the Gpce web: (See TWikiAccessControl)
- Set DENYWEBVIEW =
- Set ALLOWWEBVIEW =
- Set DENYWEBCHANGE =
- Set ALLOWWEBCHANGE = GpceorgGroup
- Set DENYWEBRENAME =
- Set ALLOWWEBRENAME = GpceorgGroup
- Users or groups allowed to change or rename this WebPreferences topic: (I.e. TWikiAdminGroup)
- Set ALLOWTOPICCHANGE = TWikiAdminGroup GpceorgGroup
- Set ALLOWTOPICRENAME = TWikiAdminGroup GpceorgGroup
- Web preferences that are not allowed to be overridden by user preferences:
- Set FINALPREFERENCES = WEBTOPICLIST, DENYWEBVIEW, ALLOWWEBVIEW, DENYWEBCHANGE, ALLOWWEBCHANGE, DENYWEBRENAME, ALLOWWEBRENAME
- A preference is defined as:
6 spaces * Set NAME = value
Example:- Set WEBBGCOLOR = #FFFFC0
- Preferences are used as TWikiVariables by enclosing the name in percent signs. Example:
- When you write variable
%WEBBGCOLOR%, it gets expanded to#D0D0D0.
- When you write variable
- The sequential order of the preference settings is significant. Define preferences that use other preferences first, i.e. set
WEBCOPYRIGHTbeforeWIKIWEBMASTERsince%WEBCOPYRIGHT%uses the%WIKIWEBMASTER%variable. - You can introduce new preferences variables and use them in your topics and templates. There is no need to change the TWiki engine (Perl scripts).
- TWikiPreferences has site-level preferences.
- TWikiUsers has a list of user topics. User topics can have optional user preferences.
- TWikiVariables has a list of common
%VARIABLES%. - TWikiAccessControl explains how to restrict access by users or groups.
Number of topics: 0
- Topic index: List of Gpce topics in alphabetical order.
|All|A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z|
| All topics in BookView |
- Jump to topic: If you already know the name of the topic, enter the name of the topic into the GoBox at the top
- WebChanges: Find out what topics in Gpce have changed recently
- How to edit text:
- Make changes to topics in GoodStyle,
- Learn the TextFormattingRules, and
- Have a look at the TextFormattingFAQ
- Topic index: List of Gpce topics in alphabetical order.
|All|A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z|
| All topics in BookView |
- Jump to topic: If you already know the name of the topic, enter the name of the topic into the GoBox at the top
- WebChanges: Find out what topics in Gpce have changed recently
- How to edit text:
- Make changes to topics in GoodStyle,
- Learn the TextFormattingRules, and
- Have a look at the TextFormattingFAQ
Statistics for TWiki.Gpce Web
force an update) * TWikiDocumentation tells you how to enable the automatic updates of the statistics. * Suggestion: You could archive this topic once a year and delete the previous year's statistics from the table.Finding topics
Tracking activity
- WebNews: selected changes
- WebChanges: recent changes
- WebNotify: email notification of changes
- WebStatistics: usage counts
- WebPreferences: values of variables
- WebContents?: web specific entries in the side bar
- CustomSiteMenus
- GpceBylaws
- ProposedBylawsBatory
- SiteMap
- SteeringCommittee
- UpdateWebPages
- WebChanges
- WebChanges100
- WebChanges200
- WebChanges500
- WebCustomMenus
- WebHome
- WebIndex
- WebLeftBar
- WebNews
- WebNotify
- WebPreferences
- WebRss
- WebSearch
- WebSearchAdvanced
- WebStatistics
- WebTools
- WebTopicList
- WebView
Welcome to the Rice PLT project on
Our current focus is on ways to address this problem by strengthening ``traditional'' multi-stage type systems using (mainly) foundational techniques from type theory and functional reactive programming (FRP) to create a paradigm of resource-aware multi-stage programming. Linear and alias types (in conjunction with dependent typing) will be used to ensure space-boundedness, new typing techniques are used to ensure time-boundedness, and signals and behaviors from FRP allow for a natural style of reactive programming.
Resource Aware Programming (RAP)
Languages for embedded software /pub/Gpce/WebView/emsp.gifIntroduction
This research group explores the impact of state-of-the-art programming languages techniques such as multi-stage programming in embedded systems. Multi-stage languages already provide significant safety guarantees. For example, a program generator written in such a language not only is type-safe in the traditional sense, but we are guaranteed that any generated program will also be type safe. This provides a noteworthy degree of assurance about the quality of the generated code. But like most traditional high-level programming techniques, multi-stage programming was designed to satisfy functional requirements rather than operational ones, and existing multi-stage languages do not provide any guarantees about the behavior of programs in the presence of bounded resources. The challenge in this setting is ensuring that the generated programs are suitable for execution on an embedded platform.Publications
- Functional Programming for Real Applications, Invited Paper (ES’01)
Resource Aware Programming
- Event-driven FRP (PADL’02)
- Real-Time FRP (ICFP’01)
Related Systems
- MetaOCaml
: A compiled, multi-stage OCaml
Openings
Team Members
Acknowledgments
Supported by NSF ITR "A Framework for Rapid Development of Reliable Robotics Software"Number of topics: 24